-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Table] Support TablePagination display of all rows #17885
Conversation
Details of bundle changes.Comparing: 0a6d9a5...c7d1129
|
docs/src/pages/components/tables/CustomPaginationActionsTable.js
Outdated
Show resolved
Hide resolved
@SarthakC In order to fix the codesandbox build fail, you will need to rebase on master. |
Sure thing |
e7f9d55
to
78bcda7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a great start. A couple of feedback:
- The page range display looks wrong
1--1 of 15
when the option to display all the rows is chosen. - The build fails you should edit the TypeScript version of the demos and run the script that generates the JavaScript version.
- We should update the TypeScript definition for the prop.
- We might want to document this feature but I'm not sure how.
[fixed] page range display for 'all' option [fixed]The page range display showed 1--1 of {totalRows} when the option to display all the rows was chosen.
57a6d59
to
4bc35bf
Compare
might need revision
9630eea
to
0ecc761
Compare
0ecc761
to
c7d1129
Compare
Well done |
@@ -125,9 +126,9 @@ const TablePagination = React.forwardRef(function TablePagination(props, ref) { | |||
<MenuItemComponent | |||
className={classes.menuItem} | |||
key={rowsPerPageOption} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey,
This line is causing following issue:
index.js:1 Warning: Encountered two children with the same key, `.$.$.$[object Object]`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version
Sorry for necroing here but while the typings were updated, the API documentation here was missed. |
@kevinlul It's documented in https://material-ui.com/components/tables/#custom-pagination-options. It would likely not fit inside the API page 🤔 |
It's not an example, it's the default value. |
Oops, I misread. I guess hyperlinking in the description cell is the only solution? |
@kevinlul Yes, if you want to open a pull request, I think that it could make sense |
fix #9136